fix(docs): correct operand terminology in instruction example #2281
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Hi, @PivasDesant, please add the corresponding changelog entry |
Collaborator
Because this PR only changes documentation, changelog entries are not necessary. Please revert the last commit and sorry for the inconvenience. |
This reverts commit 9e5280f.
Author
|
@gabrielbosio done, no inconvenience whatsoever, thanks for the review! |
gabrielbosio
approved these changes
Jan 26, 2026
Collaborator
|
@PivasDesant This commit has to be signed otherwise I can't merge this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix operand naming in instruction example - should be op0/op1, not op1/op2.